The name should be state-image for consistency.

MAYBE we can also use one click handler for all elements

One click handler per element is a lot easier to reason about.

I added a separate one for images because images allow service calls where the others don't. We could allow service calls for the other element types too, or check the type in the handler if it's trying to call a service. I'll go with whatever solution you guys decide on though

Also, @c727 I didn't use state-image because I was concerned people would get confused if they weren't trying to setup state_images. I will change it if you'd rather keep the naming consistent for all elements though

yep, I thought someone might also wants to use servicecalls on the other state-elements instead of toggle/dialog, but we can also change this later.

If I suggest changes I'm always open for discussion, not every suggestion must be good :P

You have done a lot more work on lovelace than me so I like to defer to your judgement, but you have to fight it out with balloob 😄

We can always add a helper method, _maybeAttachCallService(element, elementConfig)

@balloob are you talking about a helper to add a separate click handler? Something like https://hastebin.com/oyuyeyifox.javascript

Yep. That way we don't need to implement that method for every element and enforce the same config

I originally went with the helper, but it seemed really redundant. We need click handlers on 3 of the element types which are the same 3 that the helper would have been wrapping since the other 3 types handle clicks differently, so I just put the service call logic in the click handler. I will change it if you still think it would be better

Looks good.